This PR resolves #335.

Summary

Fixes a bug where the configuration line appended to .bashrc by inshellisense lacks a trailing newline. This results in broken command concatenation if another tool (e.g., CUDA) appends config lines immediately after.

What Changed

In src/commands/init.ts, added an explicit trailing newline to the config output:

process.stdout.write(`\n\n${config}\n`);

Why It Matters

Without a newline, tools appending shell config to .bashrc (e.g., CUDA) may cause a malformed entry like:

[ -f ~/.inshellisense/bash/init.sh ] && source ~/.inshellisense/bash/init.shexport PATH=...

This breaks shell startup and leads to errors like:

bash: /home/user/.inshellisense/bash/init.shexport: No such file or directory

Environment

• OS: Ubuntu 24.04.2 LTS
• Shell: Bash 5.2.21
• Node: 22.15.0
• is version: 0.0.1-rc.20